0.0
NA
CVE-2025-63387
Dify Console API Insecure Authorization Vulnerability
Description

Dify v1.9.1 is vulnerable to Insecure Permissions. An unauthenticated attacker can directly send HTTP GET requests to the /console/api/system-features endpoint without any authentication credentials or session tokens. The endpoint fails to implement proper authorization checks, allowing anonymous access to sensitive system configuration data.

INFO

Published Date :

Dec. 18, 2025, 7:16 p.m.

Last Modified :

Dec. 18, 2025, 7:16 p.m.

Remotely Exploit :

No
Affected Products

The following products are affected by CVE-2025-63387 vulnerability. Even if cvefeed.io is aware of the exact versions of the products that are affected, the information is not represented in the table below.

No affected product recoded yet

Solution
Implement proper authorization checks for the /console/api/system-features endpoint.
  • Enforce authentication on all API endpoints.
  • Validate user permissions before access.
  • Restrict access to sensitive data.
  • Update Dify to a secure version.
References to Advisories, Solutions, and Tools

Here, you will find a curated list of external links that provide in-depth information, practical solutions, and valuable tools related to CVE-2025-63387.

URL Resource
https://gist.github.com/Cristliu/cddc0cbbf354de51106ab63a11be94af
https://github.com/langgenius/dify/discussions
CWE - Common Weakness Enumeration

While CVE identifies specific instances of vulnerabilities, CWE categorizes the common flaws or weaknesses that can lead to vulnerabilities. CVE-2025-63387 is associated with the following CWEs:

Common Attack Pattern Enumeration and Classification (CAPEC)

Common Attack Pattern Enumeration and Classification (CAPEC) stores attack patterns, which are descriptions of the common attributes and approaches employed by adversaries to exploit the CVE-2025-63387 weaknesses.

We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).

Results are limited to the first 15 repositories due to potential performance issues.

The following list is the news that have been mention CVE-2025-63387 vulnerability anywhere in the article.

The following table lists the changes that have been made to the CVE-2025-63387 vulnerability over time.

Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.

  • New CVE Received by [email protected]

    Dec. 18, 2025

    Action Type Old Value New Value
    Added Description Dify v1.9.1 is vulnerable to Insecure Permissions. An unauthenticated attacker can directly send HTTP GET requests to the /console/api/system-features endpoint without any authentication credentials or session tokens. The endpoint fails to implement proper authorization checks, allowing anonymous access to sensitive system configuration data.
    Added Reference https://gist.github.com/Cristliu/cddc0cbbf354de51106ab63a11be94af
    Added Reference https://github.com/langgenius/dify/discussions
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days. Following chart shows the EPSS score history of the vulnerability.
Vulnerability Scoring Details
No CVSS metrics available for this vulnerability.